Skip to content

fix(useWorker): prevent multiple renders triggered by update#17

Merged
fjcaetano merged 1 commit into
masterfrom
fix/worker
Dec 2, 2019
Merged

fix(useWorker): prevent multiple renders triggered by update#17
fjcaetano merged 1 commit into
masterfrom
fix/worker

Conversation

@fjcaetano
Copy link
Copy Markdown
Owner

This fixes an issue where updating isLoading and error would trigger multiple render since those were two different states.

fix #16

@fjcaetano fjcaetano added the bug Something isn't working label Nov 26, 2019
@fjcaetano fjcaetano added this to the 1.0.0 milestone Nov 26, 2019
@codecov-io
Copy link
Copy Markdown

codecov-io commented Nov 26, 2019

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master    #17   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines          68     69    +1     
  Branches        6      6           
=====================================
+ Hits           68     69    +1
Impacted Files Coverage Δ
src/index.tsx 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0d9153a...d7fccd5. Read the comment docs.

This fixes an issue where updating `isLoading` and `error` would trigger multiple render since those were two different states.

fix #16
@fjcaetano fjcaetano merged commit 9f1ee5f into master Dec 2, 2019
@fjcaetano fjcaetano deleted the fix/worker branch December 2, 2019 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] useWorker updates trigger multiple renders

2 participants